home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
pc_board
/
ulp092b.zip
/
ULP.CFG
< prev
next >
Wrap
Text File
|
1992-03-29
|
17KB
|
375 lines
;
;
; ┌───────────────────┐
; │ │ ║ UpLoadProcessor Configuration File
; │ ╥ ╥ ╥ │ ║
; │ ║ ║ ║ ╓──╖ │ ║ Version 0.92ß
; │ ║ ║ ║ ║ ║ │ ║
; │ ╙───╜ ╨ ║──╜ │ ║ (c) Copyright 1992 - Stacy Smith
; │ ╨ │ ║
; └───────────────────┘ ║
; ════════════════════╝
;
; The latest version of ULP can always be obtained from my BBS:
;
; The Bloom Beacon-Picayune BBS
; (804) 525-9760
; 300-14,400 Baud (USRobotics V.32bis)
; FidoNet 1:276/112 (magic tags ULP and ULP286)
;
; NOTE: I have tried to make this configuration file as flexible as possible,
; but it would probably be a good idea to not rearrange it too much if
; it can be avoided...
;
;
; ╔════════════════════════════════════╗
; ║ General Options And Parameters ║
; ╚════════════════════════════════════╝
;
; The registration code, BBS name and sysop name EXACTLY as provided to you on
; your registration letter. If this is an unregistered version, comment out
; these lines, or don't change them. Note that these are case-sensitive!
REG_CODE 0000000000
BBS_NAME UNREGISTERED
SYSOP_NAME SYSOP
; The size of the disk I/O buffers you wish to allocate in bytes (valid values
; are between 2048 bytes and 16384 bytes). Optimal performance is obtained with
; a value that is a multiple of 2048 (a typical hard disk cluster size).
DISK_BUFFER 8192
; The path/filename of the log file for ULP to record its activities. Comment
; out if you don't want disk logging.
LOG_FILE c:\ulp\ulp.log
; If you want ULP and ULPTEST to record their statistics on each archive
; processed to the log file, add the VERBOSE keyword. If you only want errors
; and summary statistics, use the TERSE keyword or comment the line out.
LOG_MODE verbose
; If you want ULP to insert internal description files (FILE_ID.DIZ or
; DESC.SDI), type YES; if not, type NO or comment the line out.
INT_DESC yes
; If ULP is to insert internal description files, the following parameter
; is the maximum number of lines that ULP will insert from the description
; file. This defaults to 10 if the line is commented out.
DESC_LIMIT 10
; If you want ULPDB to use a specific directory for decompressing archives
; while generating the database, place the pathname (including the trailing
; backslash). This directory must exist. If you do not desire to use a
; specific directory, comment it out (ULPDB will extract at its current
; location on disk).
WORK_DIR c:\temp\
; This defines how ULP dispositions archives found to have an error other than
; a file check failure (such as ZIP CRC). If you want ULP to delete the archive
; and description, type DELETE; if you want ULP to rename the archive to a .ERR
; extension, type RENAME or comment the line out.
ERR_DISP rename
; This defines how ULP dispositions archives that fail a file check, such as a
; virus scan. If you want ULP to delete the archive and description, type
; DELETE; if you want ULP to rename the archive to a .VRS extension, type
; RENAME or comment the line out.
VIRUS_DISP delete
; If you want ULP and ULPTEST to screen ARC, PAK, ZIP and ZIP SFX archives for
; DOS reserved keywords prior to unpacking them, type YES or comment the line
; out, otherwise, type NO. This will prevent someone from hanging your system
; by hex-editing one of these archives and replacing a filename with a DOS
; reserved device keyword.
SCREEN_ARC yes
; The command line for an ASCII file viewing (or editing) utility. This will
; be called by ULPDB in order to view an archive information file generated
; for the purposes of archive review. Place the @FILES@ variable where the
; filename is to be entered on the utility's command line.
VIEWER list @FILES@
;
;
; ╔════════════════════════╗
; ║ Upload Directories ║
; ╚════════════════════════╝
;
; Each pair of upload directories (one private, and one public), is denoted by
; UL_DIR x, where x is a sequential number. Up to 10 directory pairs can be
; processed by ULP. The next 6 keywords are required after the UL_DIR statement;
; do not comment any of them out or insert other parameters or comments in
; between them:
; UL_DIR = denotes a new directory pair.
; SOURCE_PATH = the directory where the private uploads are placed by the BBS.
; Note: this must include the trailing backslash!
; SOURCE_LIST = the private upload directory list file that contains the archive
; descriptions, including the path.
; SOURCE_HDR = the number of lines to ignore at the beginning of the private
; upload directory list file (for headers, detachable header
; filespecs, etc.)
; DEST_PATH = the directory where the public uploads are placed by ULP after
; successful processing. Note: this must include the trailing
; backslash!
; DEST_LIST = the public upload directory list file that contains the archive
; descriptions, including the path. ULP will append this file
; with the descriptions of successfully processed files.
; DEST_HDR = the number of lines to ignore at the beginning of the public
; upload directory list file (for headers, detachable header
; filespecs, etc.)
UL_DIR 1
SOURCE_PATH c:\privul\
SOURCE_LIST c:\pcb\gen\prvuldir
SOURCE_HDR 1
DEST_PATH c:\publul\
DEST_LIST c:\pcb\gen\newuldir
DEST_HDR 1
;
;
; ╔════════════════════════╗
; ║ Age Limit Checking ║
; ╚════════════════════════╝
;
; If you want ULP to fail an archive based on the date of its most recent
; file, type YES; if not, type NO or comment the line out.
AGE_CHK yes
; The maximum age in months, that you will accept as an upload.
AGE_LIMIT 48
;
;
; ╔═════════════════════════════╗
; ║ Archiving Control Flags ║
; ╚═════════════════════════════╝
;
; If you want ULP to convert the archive to a default archiving format of your
; choice, type YES; if not, type NO or comment the line out.
ARC_CVT yes
; If you want ULP to convert any internal archives within the archive to your
; default archiving format, type YES; if not, type NO or comment the line out.
; This may save some disk space, but will potentially mess up any automatic
; installation programs/batch files contained within the archive.
ARC_NEST_CVT no
; If you want ULP to convert a self-extracting (SFX) archive to your default
; archiving format, type YES; if not, type NO or comment the line out. This
; also may save some disk space, but can cause problems. For example, if you
; don't have PKZ110.EXE on your BBS, a novice user has no way of obtaining the
; PKZIP/PKUNZIP utilities from your BBS.
SFX_CVT no
; If you want ULP to keep ZIP archives with authenticity verification stamps
; (-AV) regardless of the other archiving control flags, then set this to 'yes'
; or comment it out. If you set this flag to 'no', then the archive will be
; recompressed per the other control flags.
KEEP_AV yes
; If you want ULP to keep ARJ archives with security envelopes (similar to a
; ZIP -AV) regardless of the other archiving control flags, then set this
; to 'yes' or comment it out. If you set this flag to 'no', then the archive
; will be recompressed per the other control flags.
KEEP_ENV yes
;
;
; ╔══════════════════════════╗
; ║ Archiver Definitions ║
; ╚══════════════════════════╝
;
; Each archiver, is denoted by ARCHIVER x, where x is a sequential number. Up
; to 10 archivers can be executed by ULP. ULP is capable of automatically
; detecting ARC, ARJ, HYP, LZH, PAK, ZIP and ZOO archives. The next 6 keywords
; are required after the ARCHIVER statement; do not comment any of them out or
; insert other parameters or comments between them. I would also advise
; against changing the command options I have set, unless you have need to do
; so. Most are to ensure uninterrupted processing (such as '/m1' in LHA).
; ARCHIVER = denotes a new archiver definition.
; ARC_EXT = the extension for this particular archiving format.
; ARC_PRIMARY = if this is the default archiving format you use on your BBS,
; type YES; if not, type NO.
; ARC_PACK = the command line to pack archives, including all command-line
; switches desired. Place the variable @ARCHIVE@ where the
; filename is to be inserted in the command line and @FILES@
; where the filespec is to be inserted. If you want a comment to
; be inserted, you must include it in the command-line switches.
; ARC_UNPACK = the command line to unpack archives, including all command-line
; switches desired. Place the variable @ARCHIVE@ where the
; filename is to be inserted in the command line.
; ARC_TEST = the command line to test archives, including all command-line
; switches desired. Place the variable @ARCHIVE@ where the
; filename is to be inserted in the command line.
; ARC_ERR = the errorlevel that the archiver returns upon success. This
; information should be available in the program's documentation.
ARCHIVER 1
ARC_EXT arc
ARC_PRIMARY no
ARC_PACK pkpak -a @ARCHIVE@ @FILES@
ARC_UNPACK pkunpak -r @ARCHIVE@
ARC_TEST pkunpak -t @ARCHIVE@
ARC_ERR 0
;
ARCHIVER 2
ARC_EXT arj
ARC_PRIMARY yes
ARC_PACK arj a -e -jm -m1 -zc:\ulp\comment.txt @ARCHIVE@ @FILES@
ARC_UNPACK arj e -y @ARCHIVE@
ARC_TEST arj t @ARCHIVE@
ARC_ERR 0
;
ARCHIVER 3
ARC_EXT hyp
ARC_PRIMARY no
ARC_PACK hyper -a @ARCHIVE@ @FILES@
ARC_UNPACK hyper -x @ARCHIVE@
ARC_TEST hyper -v @ARCHIVE@
ARC_ERR 0
;
ARCHIVER 4
ARC_EXT lzh
ARC_PRIMARY no
ARC_PACK lha a /m1 @ARCHIVE@ @FILES@
ARC_UNPACK lha e /m1 @ARCHIVE@
ARC_TEST lha t /m1 @ARCHIVE@
ARC_ERR 0
;
ARCHIVER 5
ARC_EXT pak
ARC_PRIMARY no
ARC_PACK pak a /h /wa @ARCHIVE@ @FILES@
ARC_UNPACK pak e /wa @ARCHIVE@
ARC_TEST pak t /wa @ARCHIVE@
ARC_ERR 0
;
ARCHIVER 6
ARC_EXT zip
ARC_PRIMARY no
ARC_PACK pkzip -a -ex -z<c:\ulp\comment.txt @ARCHIVE@ @FILES@
ARC_UNPACK pkunzip -o @ARCHIVE@
ARC_TEST pkunzip -t @ARCHIVE@
ARC_ERR 0
;
ARCHIVER 7
ARC_EXT zoo
ARC_PRIMARY no
ARC_PACK zoo ahP @ARCHIVE@ @FILES@
ARC_UNPACK zoo e @ARCHIVE@
ARC_TEST zoo t @ARCHIVE@
ARC_ERR 0
;
;
; ╔═══════════════════════════════════╗
; ║ Uncompressed Files to Process ║
; ╚═══════════════════════════════════╝
;
; ULP can process selected uncompressed uploads, using the PROC_EXT option.
; Up to 10 uncompressed file types can be specified by extension. DO NOT
; use any compression format extensions (ARJ, ZIP, etc.). If you do not
; want to process any uncompressed uploads, simply remove or comment out
; the lines.
PROC_EXT com
PROC_EXT doc
PROC_EXT txt
;
;
; ╔══════════════════════════════════════════╗
; ║ File Checking (Virus Scanning, etc.) ║
; ╚══════════════════════════════════════════╝
;
; Each file checker is denoted by FILE_CHECKER x, where x is a sequential
; number. Up to 5 file checking programs can be executed by ULP. The next 2
; keywords are required after the FILE_CHECKER statement; do not comment them
; out or insert other parameters or comments in between them.
; FILE_CHECKER = denotes a new file checking/virus program definition.
; FILE_CHK_CMD = the command line to execute each file checker, including all
; command-line switches. Place the variable @FILES@ where the
; filespec is to be placed on the command line.
; FILE_CHK_ERR = the errorlevel that the file checking program returns upon
; success. This information should be available in the
; program's documentation.
FILE_CHECKER 1
FILE_CHK_CMD scan /a /nomem /nopause @FILES@
FILE_CHK_ERR 0
;
;
; ╔═══════════════════════╗
; ║ GIF File Checking ║
; ╚═══════════════════════╝
;
; Each GIF file checker is denoted by GIF_CHECKER x, where x is a sequential
; number. Up to 5 GIF file checking programs can be executed by ULP. The next
; 2 keywords are required after the GIF_CHECKER statement; do not comment
; them out or insert other parameters or comments in between them.
; GIF_CHECKER = denotes a new file checking/virus program definition.
; GIF_CHK_CMD = the command line to execute each GIF file checker, including
; all command-line switches. Place the variable @FILES@ where
; the filespec is to be placed on the command line.
; GIF_CHK_ERR = the errorlevel that the GIF file checking program returns
; upon success. This information should be available in the
; program's documentation.
GIF_CHECKER 1
GIF_CHK_CMD c:\giftest\giftest /b:0 @FILES@
GIF_CHK_ERR 0
;
;
; ╔═════════════════════════════════════════╗
; ║ Archive Information Line Parameters ║
; ╚═════════════════════════════════════════╝
;
; If you want ULP to add a single line to the archive description, type YES;
; if not, type NO or comment the line out.
INFO_LINE yes
; The column where the | marker goes in your directory listing setup. The
; standard PCBoard setup indents to column 32.
INFO_INDENT 32
; The format that you would like for the information line. The legal variables
; are: @#@ Number of files in the archive (and nested archives)
; @NEWEST@ Date of the newest file in the archive
; @OLDEST@ Date of the oldest file in the archive
; @BYTES@ The total number of bytes (uncompressed) in the archive
INFO_FORMAT (Files: @#@ Newest: @NEWEST@ Oldest: @OLDEST@)
;
;
; ╔════════════════════════════════╗
; ║ ULPTEST Testing Parameters ║
; ╚════════════════════════════════╝
;
; This defines how ULPTEST processes archives. NORMAL indicates a full test
; is to be performed, identical to the ULP event processing except that the
; archive formats are not converted (this is a limitation of PCBoard).
; FAST indicates a fast test in which the archive is scanned for archive
; integrity, duplicates, and age without unpacking the archive (ARJ and ZIP
; files only). If this mode is used, it should be held for later processing
; by ULP so that it can be file-checked.
TEST_MODE normal
; If NORMAL mode is used, the archive's file size will first be compared
; against this limit (in kilobytes). If it is larger than this number of
; bytes (in kilobytes), it will be forced into FAST mode to speed the process
; and prevent wasting the user's online time. Entering 0, or commenting the
; line out will disable this feature.
TEST_LIMIT 250
; If you want ULPTEST to output status information to the user on-line, set
; the following to YES; if not, enter NO or comment the line out.
COMM_IO yes
;
;
; ╔══════════════════════════╗
; ║ BBS Ads File Removal ║
; ╚══════════════════════════╝
;
; If you want ULP to remove known BBS ads from new uploads during processing,
; type YES; if not, type NO or comment the line out.
ADS_CHK yes
; The directory path and name for the BBS ads database.
ADS_DB c:\ulp\ulpads.db
;
;
; ╔═══════════════════════════════╗
; ║ CRC-32 Duplicate Checking ║
; ╚═══════════════════════════════╝
;
; If you want ULP to use its internal CRC-32 duplication checking, type YES;
; if not, type NO or comment the line out. If you want to use a third-party
; duplication checker, such as ZDCS, you can add it as a file checker (above),
; providing it returns DOS errorlevels so ULP can detect its success/failure.
DUPE_CHK yes
; The maximum percentage of duplication allowed for a file to pass. Anything
; larger will fail. This number should be at least 50, as some program authors
; don't modify every file, especially with maintenance releases.
DUPE_LIMIT 75
; The directory path listing file for database generation. Generally, this
; will the DLPATH.LST file defined in PCBOARD.DAT.
DUPE_LIST c:\ulp\dlpath.lst
; The path and name for the main CRC-32 database file.
DUPE_DB c:\ulp\database.db
; The path and name for the main CRC-32 database file index.
DUPE_IDX c:\ulp\database.idx
; If you want ULP and ULPTEST to validate the CRC-32 database before using
; it, comment the line out or answer 'YES', otherwise answer 'NO'.
DB_VALIDATE yes
;
; End of ULP configuration file...
;